Skip to content

Abhishek/refactor to use react query#816

Closed
asharma12-sonata wants to merge 41 commits into
openedx:masterfrom
edx:abhishek/refactor-to-use-react-query
Closed

Abhishek/refactor to use react query#816
asharma12-sonata wants to merge 41 commits into
openedx:masterfrom
edx:abhishek/refactor-to-use-react-query

Conversation

@asharma12-sonata
Copy link
Copy Markdown

@asharma12-sonata asharma12-sonata commented Mar 30, 2026

Please refer to the below link for more description.

#751 (comment)

Apart from the description given above, we have moved APIs from redux to use react-query.

MaxFrank13 and others added 30 commits October 15, 2025 15:46
)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Maxwell Frank <92897870+MaxFrank13@users.noreply.github.com>
)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…#783)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…edx#784)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@openedx-webhooks
Copy link
Copy Markdown

Thanks for the pull request, @asharma12-sonata!

This repository is currently maintained by @2U-aperture.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@mphilbrick211
Copy link
Copy Markdown

Hi @asharma12-sonata! Thanks for this contribution. You will need to complete a CLA form in order to get this pull request merged. If you are contributing as an individual, you can complete the individual CLA form here. If you are contributing on behalf of an organization (Sonata), please have your manager reach out to oscm@axim.org so we can add you to our existing entity agreement. Thanks!

@mphilbrick211 mphilbrick211 moved this from Needs Triage to Needs Tests Run or CLA Signed in Contributions Mar 30, 2026
@mphilbrick211 mphilbrick211 moved this from Needs Tests Run or CLA Signed to Waiting on Author in Contributions Apr 6, 2026
@mphilbrick211
Copy link
Copy Markdown

@asharma12-sonata your CLA check is all set, but there are some failing checks to take a look at when you have a minute.

@github-project-automation github-project-automation Bot moved this from Waiting on Author to Done in Contributions Apr 10, 2026
@asharma12-sonata asharma12-sonata deleted the abhishek/refactor-to-use-react-query branch April 10, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

7 participants